Hello to all.

Original topic: hxxp://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/sfc-verifyfile-doesnt-work-is-it-a-bug/17542cd5-1eee-4cb1-948c-d9ff68267e3a

I found that SFC /VERIFYFILE doesn't work on my machine.

I can't know if it doesn't work on each Windows 8/8.1 machine.

I saw this when I was trying to verify a well-known file prone to corruption (it is at least an year that this keeps to corrupt itself): CNBJ2530.DPB.

That file becomes corrupt for unknown reasons, from time to time.

Usually you can find Windows corrupt files through SFC /SCANNOW, wait for about half hour and check the CBS.LOG.

Given that the corrupt file is always THAT, I decided to try SFC /VERIFYFILE (few months ago), to save time.

To my surprise, it didn't work:

sfc /verifyfile=C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\cnbj2530.dpb
Windows Resource Protection could not perform the requested operation.
(Italian: Protezione risorse di Windows: impossibile eseguire l'operazione richiesta.)

Yes, I used an elevated command prompt.

Yes, I've tried with double quotes... And single quotes, too.

The questions are: Doesn't it work just for me? Or Doesn't it work for everybody?

Thanks in advance for any replies and/or confirmations.



Operating System: Windows 8.1 x64 update 1.

- I changed the Windows font size from Control Panel\Appearance and Personalisation\Display, change the size of all items, larger (150%).

- I changed the setting NX=AlwaysOn (DEP always on), by:

bcdedit /set {current} nx AlwaysOn

- I modified the default rules of the firewall (I exported the standard criteria and saved in a file), created my own rules, blocked all outgoing connections (except those I created with my rules).

• Edited by xilolee 18 hours 4 minutes ago

Xilolee

Given that I do not have that file it is impossible to tell.  There are however over 3500 hits on a search of that file causing corruption but I cannot find what that file is associated with.

SFC /verifyfile on 8.1 with other files is not a problem.

Hi Wanikiya and Dyami and thanks for your answer.

Are you saying that command works on your system, even if the file is another one?

I have now tried that command on various files inside the c:\Windows\system32 folder, and it seems to work (and I'm partially happy :-) ).

Hence the questions are now:

- Should it only work for the files in c:\windows\system32 folder?

- Should it always fail for the files in C:\Windows\Winsxs\ folder?

Because the corrupted files are usually found in this one...

• Edited by xilolee 7 hours 6 minutes ago

However, notwithstanding the above, to fix the root cause of your corruption problem (which I have seen too with prncacla) try the DISM command. Specifically:

DISM /Online /Cleanup-Image /RestoreHealth

After the above completes, do again an SFC /SCANNOW command, and your servicing database should again be in good shape.

-Noel